Conversation
0772828 to
f9f51f8
Compare
|
@darrenkopp I hope you don't mind that I have taken over your project files from https://github.com/darrenkopp/sassc-win? I think it should work correctly now. Took me quite some time to figure out why it was giving me strange results with the test runner (seems ruby 1.9 was the cause). Beside that everything seems to work now. Once the PR on sassc is merged I can remove the reference to my local sassc repository! Also the debug target on msvc throws some debug assertions, which seem to keep the build on hold forever till it times out. So I disabled the test-runner on that target. |
|
Yup, no worries. |
|
Awesome! :) @mgreter, separately, TravisCI has beta OSX testing support too. Based on this, you would need to send them an email (support@travis-ci.com) to enable Mac testing for libsass repo. I contacted them for node-sass, but they denied saying:
I think they might enable it for libsass, as there is no such issue. |
Made windows mingw compliation working:
https://ci.appveyor.com/project/mgreter/libsass/build/1.0.25
Needs sass/sassc#83 to be merged first!